- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 33.6k
test_runner: fix coverage report when --enable-source-maps is provided #55228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| Review requested: 
 | 
| I bring with me my concerns from the other PR, but I'm curious what others think | 
| 
 Now I see what you meant. I will dig into it. | 
4b1fa1f    to
    c8bd13f      
    Compare
  
    c8bd13f    to
    67517de      
    Compare
  
    | Codecov ReportAttention: Patch coverage is  
 
 Additional details and impacted files@@            Coverage Diff             @@
##             main   #55228      +/-   ##
==========================================
- Coverage   88.41%   88.40%   -0.02%     
==========================================
  Files         652      652              
  Lines      186756   186785      +29     
  Branches    36100    36101       +1     
==========================================
- Hits       165126   165119       -7     
- Misses      14906    14931      +25     
- Partials     6724     6735      +11     
 | 
| 
 how's this possible? | 
c0deb06    to
    51c8f37      
    Compare
  
    | 
 In my experience, codecov isn't always exactly accurate. Regardless, it's nothing to be concerned about. | 
51c8f37    to
    ed3668e      
    Compare
  
    | 
 If you can reproduce the failure locally, it might help to have it log the output to see what the actual difference is. | 
| 
 It's the assertion on stdout this message is not being printed. When I run  Sorry @redyetidev . Newbie working. I think I need to recompile | 
| Try rebasing to include your other PR? | 
ed3668e    to
    6391e6e      
    Compare
  
    | Landed in 3a42085 | 
| This Refs two issues. Does it actually fix either/both of them? | 
| 
 I'd say yes. I'm pretty sure it solves #54753. Could you confirm for #55106 @redyetidev ? | 
| There aren't any tests to confirm that, can you no longer reproduce the errors described? I would assume your other PR fixes that one | 
PR-URL: #55228 Refs: #55106 Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Chemi Atlow <[email protected]>
PR-URL: nodejs#55228 Refs: nodejs#55106 Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Chemi Atlow <[email protected]>
PR-URL: nodejs#55228 Refs: nodejs#55106 Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Chemi Atlow <[email protected]>
Refs: #55106 #54753